Skip to content

Graphics team updates#16499

Merged
joethreepwood merged 5 commits intomasterfrom
lottie-handbook
Apr 23, 2026
Merged

Graphics team updates#16499
joethreepwood merged 5 commits intomasterfrom
lottie-handbook

Conversation

@joethreepwood
Copy link
Copy Markdown
Contributor

Changes

Introduces the Graphics team and restructures the handbook navigation

Lottie now leads a new team called Graphics, alongside Daniel Hawkins and Heidi. All three have moved off the Marketing team. This PR updates the handbook to reflect that change and reorganises the navigation. It also hits some other minor points of clarification.

Team changes

  • Renamed the "Brand & Design" handbook section to "Graphics" because Brand & Design isn't a team
  • Updated brand/overview to describe the Graphics team's remit: owning all illustration, art, and brand at PostHog, with final say on those matters. Clarifies the team does not own product or website design
  • Updated brand/art-requests to attribute Lottie, Heidi, and Daniel to the Graphics team rather than Marketing
  • Updated marketing/index to describe how the six marketing-adjacent teams work together: Graphics, Website, Marketing, Editorial, YouTube, and Docs & Wizard

Navigation restructure

  • Renamed "PostHog.com" nav section to "Website" so it fits the naming convention of other teams
  • Moved "Product design for engineers" and "Product design process" out of the Graphics/Brand section and into Engineering, where they logically belong
  • Sorted all top-level sections in the handbook Resources area alphabetically: Blitzscale, Content, Docs & Wizard, Engineering, Graphics, Growth, Marketing, People & Ops, Product, RevOps, Sales CS & Onboarding, Support, Website

Other updates

  • marketing/ownership: general marketing questions now directed to #group-marketing-and-content instead of #team-marketing
  • handbook/brand/process moved to handbook/engineering/product-design-process, with a redirect in place for existing links (including newsletter references)

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 21, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Apr 23, 2026 01:17PM

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 21, 2026

Vale prose linter → found 7 errors, 26 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/handbook/brand/art-requests.md — 1 errors, 2 warnings, 0 suggestions
Line Severity Message Rule
23:128 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
25:15 warning 'automations' is a possible misspelling. PostHogBase.Spelling
29:17 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
contents/handbook/engineering/product-design.md — 1 errors, 6 warnings, 0 suggestions
Line Severity Message Rule
11:4 warning 'v0.1 or v2?' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
17:5 warning 'v0.1' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
19:232 warning Use American English. Use 'judgment' instead of 'judgement'. PostHogBase.AmericanEnglish
21:5 warning 'MVP' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
27:5 warning 'v2' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
39:107 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
57:226 warning 'UIs' is a possible misspelling. PostHogBase.Spelling
contents/handbook/marketing/index.md — 0 errors, 14 warnings, 0 suggestions
Line Severity Message Rule
12:46 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
13:76 warning 'Influencers' is a possible misspelling. PostHogBase.Spelling
28:46 warning Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. PostHogBase.ProductNames
28:149 warning Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. PostHogBase.ProductNames
56:19 warning 'comms' is a possible misspelling. PostHogBase.Spelling
62:99 warning 'clickbaity' is a possible misspelling. PostHogBase.Spelling
92:66 warning 'Combinator' is a possible misspelling. PostHogBase.Spelling
98:184 warning 'superfans' is a possible misspelling. PostHogBase.Spelling
106:15 warning 'influencers' is a possible misspelling. PostHogBase.Spelling
106:72 warning 'influencers' is a possible misspelling. PostHogBase.Spelling
106:90 warning 'Theo' is a possible misspelling. PostHogBase.Spelling
106:99 warning 'Fireship' is a possible misspelling. PostHogBase.Spelling
114:143 warning Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. PostHogBase.ProductNames
120:134 warning Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. PostHogBase.ProductNames
contents/handbook/marketing/ownership.md — 2 errors, 3 warnings, 0 suggestions
Line Severity Message Rule
42:64 warning 'backlink' is a possible misspelling. PostHogBase.Spelling
56:13 warning 'influencer' is a possible misspelling. PostHogBase.Spelling
88:27 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
88:77 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
112:22 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
contents/handbook/wide-company.md — 3 errors, 1 warnings, 0 suggestions
Line Severity Message Rule
32:147 warning 'autononomy' is a possible misspelling. PostHogBase.Spelling
34:511 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
36:24 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
50:184 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash

Comment thread contents/handbook/engineering/product-design-process.md Outdated
Copy link
Copy Markdown
Collaborator

@lottiecoxon lottiecoxon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have left one comment about dribbble but aside from that it's great thank you for doing this Joe!!!

Co-authored-by: Joe Martin <84011561+joethreepwood@users.noreply.github.com>
@charlescook-ph
Copy link
Copy Markdown
Collaborator

@joethreepwood Claude tells me:

  • The old file contents/handbook/brand/process.md was NOT deleted. The PR description says the page was "moved," but the diff only adds contents/handbook/engineering/product-design-process.md and adds a vercel.json redirect from /handbook/brand/process → /handbook/engineering/product-design-process. Because the source MDX still exists, Gatsby will generate a page at /handbook/brand/process and the vercel.json redirect will be shadowed/bypassed — so instead of a redirect you'll end up with two near-identical pages at two URLs. Newsletter references in contents/newsletter/bad-behaviors.md and contents/newsletter/how-to-not-breakup-with-your-cofounder.md still point at the old URL and will resolve (via the stale page), but not via the intended redirect.
  • the new product-design-process.md ends with a ## Portfolio heading with nothing under it.

@joethreepwood joethreepwood enabled auto-merge (squash) April 23, 2026 13:07
@joethreepwood joethreepwood merged commit 55d42e1 into master Apr 23, 2026
19 checks passed
@joethreepwood joethreepwood deleted the lottie-handbook branch April 23, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants